home *** CD-ROM | disk | FTP | other *** search
- Path: news.aimnet.com!news
- From: JNavas@NavasGrp.com (John Navas)
- Newsgroups: comp.dcom.modems
- Subject: Re: Cybercom and WFWG?
- Date: Sat, 20 Apr 1996 18:32:15 GMT
- Organization: The Navas Group of Dublin, CA, USA
- Message-ID: <31792c5e.10038708@news.aimnet.com>
- References: <3178ef77.246887@eskinews.eskimo.com> <317913A4.2E3D@cerberus-sys.com>
- NNTP-Posting-Host: dial-bp1-28.iway.aimnet.com
- X-Newsreader: Forte Free Agent 1.1/16.198
-
- [Posted to comp.dcom.modems]
- "Albert P. Belle Isle" <belleisl@cerberus-sys.com> wrote:
-
- >In both cases, the comm.drv is an installable driver type of Dynamically-Linked Library
- >(dll), which has 16-bit, Ring3- (applications-) level access to hardware resources
- >through a lot of Windows-style cooperative multi-tasking overhead.
-
- On the contrary -- COMM.DRV actually services the comm interrupts,
- somethings that was added in Windows 3.1 as compared to 3.0.
-
- >If you have overruns, you'll probably find that their cure is associated with the
- >configuration of the rest of your system (FIFO-equipped com port, windows system.ini
- >settings, video card driver, hard disk driver, BIOS, etc.), especially those subsystems
- >whose IRQs have a higher priority than com port IRQs, and can keep the CPU too busy to
- >empty the com port in time.
-
- IRQ priority is relatively unimportant. What is important is how long an
- interrupt service routine, or other hardware routine (e.g., in certain S3
- video drivers), keeps interrupts completely disabled, which locks out higher
- priority interrupts as well as lower priority interrupts.
-
- --
- Best regards,
- John mailto:JNavas@NavasGrp.com http://web.aimnet.com/~jnavas/
- 28800 Modem FAQ: http://web.aimnet.com/~jnavas/modem/faq.html
-